Self-Correcting vs Self-Perpetuating
Original Post
I'm finding that Column 2 abuse is NOT self-correcting, but rather self-perpetuating. What are you all finding?
For example, if I put just a few too many urgent items in C2, then I get stuck on that page. And I get stuck on the next page, too. It starts to take nearly all day to get through a page or two. Too slow.
Meanwhile, lots of new items are piling up at the end of the list -- getting further and further away. I start to become afraid that it will take me too long to get to them, since I am stuck on my current page, somewhere in the middle of the notebook. So, I start entering one or two of them into my current C2, as "urgent" items (using Mark's definition of urgent = "you want to get to it before you would through the normal processing of the list").
Of course that just slows everything down more, since I have even more C2 items I must action at each turn of the page.
Eventually this just crashes.
Personally, I don't find "system crash" to equate to "self-correcting". The system crashing and forcing me to start over from scratch doesn't really help. I know, because when I restart the system, I eventually fall into the same pattern. And the system crashes again!
I am trying to see if I can come up with a way to make this actually self-correcting -- meaning, if you start to get stuck somewhere, and your C2 starts to fill up, the system will automatically react and somehow start to force you along more quickly. Maybe through triggering more dismissals. Maybe through forcing you to turn pages more quickly somehow. But I want this to be RULE-BASED, not "common-sense" based. I want the SYSTEM to teach me how to stop crashing it, just by following the rules of the system.
This is why I am trying Mark's experiment for myself, of entering urgent items on C2 of the NEXT page. Mark said that would make things move more quickly. Maybe that's what a person should do automatically, whenever you find it takes more than a day to turn the pages through your whole list.
None of this is intended as criticism of Mark - not by any means - I have the deepest respect for him, and am so thankful for all the work he's done. I just want to see if I can make this system work for me more effectively, as a SYSTEM, not with frequent "common sense overrides" (since I don't have much of that, when I am buried with crises), and not with piles of idiosyncratic "tweaks" but with one or two very simple "adjustments" that follow the spirit of the original rules.
For example, if I put just a few too many urgent items in C2, then I get stuck on that page. And I get stuck on the next page, too. It starts to take nearly all day to get through a page or two. Too slow.
Meanwhile, lots of new items are piling up at the end of the list -- getting further and further away. I start to become afraid that it will take me too long to get to them, since I am stuck on my current page, somewhere in the middle of the notebook. So, I start entering one or two of them into my current C2, as "urgent" items (using Mark's definition of urgent = "you want to get to it before you would through the normal processing of the list").
Of course that just slows everything down more, since I have even more C2 items I must action at each turn of the page.
Eventually this just crashes.
Personally, I don't find "system crash" to equate to "self-correcting". The system crashing and forcing me to start over from scratch doesn't really help. I know, because when I restart the system, I eventually fall into the same pattern. And the system crashes again!
I am trying to see if I can come up with a way to make this actually self-correcting -- meaning, if you start to get stuck somewhere, and your C2 starts to fill up, the system will automatically react and somehow start to force you along more quickly. Maybe through triggering more dismissals. Maybe through forcing you to turn pages more quickly somehow. But I want this to be RULE-BASED, not "common-sense" based. I want the SYSTEM to teach me how to stop crashing it, just by following the rules of the system.
This is why I am trying Mark's experiment for myself, of entering urgent items on C2 of the NEXT page. Mark said that would make things move more quickly. Maybe that's what a person should do automatically, whenever you find it takes more than a day to turn the pages through your whole list.
None of this is intended as criticism of Mark - not by any means - I have the deepest respect for him, and am so thankful for all the work he's done. I just want to see if I can make this system work for me more effectively, as a SYSTEM, not with frequent "common sense overrides" (since I don't have much of that, when I am buried with crises), and not with piles of idiosyncratic "tweaks" but with one or two very simple "adjustments" that follow the spirit of the original rules.
Reply by avrum
Right now I'm the pariah on these boards, so I apologize if my response kills your thread.
<>
Yup, as do I. When I'm working without a system, I choose tasks by oscillating between pleasure/pain and commonsense. It works well-ish. However I feel more mindful and organized when operating within a system.
<
Yup, as do I. When I'm working without a system, I choose tasks by oscillating between pleasure/pain and commonsense. It works well-ish. However I feel more mindful and organized when operating within a system.
Reply by Alan Baljeu
I don't consider you a pariah, nor can I fathom why you expect this answer would kill the thread.
I've observed the cumulative effect of C2 myself. It does self correct only in that bad usage yields bad results and you learn from that. My suggested remedy is to drop most of the unfinished tasks and resume with a workable load. Second, knowing the required behaviour, set your mind to operate accordingly, and the problem won't arise.
To state it again: SF is a game, and your strategy is to minimize use of C2 but still get stuff done.
I've observed the cumulative effect of C2 myself. It does self correct only in that bad usage yields bad results and you learn from that. My suggested remedy is to drop most of the unfinished tasks and resume with a workable load. Second, knowing the required behaviour, set your mind to operate accordingly, and the problem won't arise.
To state it again: SF is a game, and your strategy is to minimize use of C2 but still get stuff done.
Reply by Don R
I've noticed a kind of oscillation of C2 as you've pointed out, but I don't know what you mean by "system crash". When I got stuck on a page, I was still doing a lot of important work. I ended up finishing or actioning everything on the page before moving on.
Reply by Seraphim
Alan wrote:
<< I've observed the cumulative effect of C2 myself. It does self correct only in that bad usage yields bad results and you learn from that. >>
That's not self-correction. It's "user" correction. In other words, the system clogs up if there are too many urgent tasks and/or unfinished tasks, so the user must change behavior to accommodate.
<< My suggested remedy is to drop most of the unfinished tasks and resume with a workable load. >>
Yes, that can work, but the problem is, the rules don't allow for that. You must invoke the "common sense rule" to operate that way. That's exactly what I'm trying to avoid. I want the rules themselves to guide me to successful use of the system.
Maybe it's an unattainable goal but still, that's what I'm looking for. :-)
<< Second, knowing the required behaviour, set your mind to operate accordingly, and the problem won't arise. >>
The problem is, this goes against three of the fundamental rules of the system:
+ "enter whatever you want into the list"
+ "work on whatever feels ready to be done"
+ "work as long as you like"
In addition to all these rules, you have to follow a whole bunch more in order to avoid C2 problems:
+ Don't enter too many urgent tasks - or handle them off-list (what if you REALLY DO have lots of urgent tasks? what if it's too complicated to handle them off-list, or you are forced to create a secondary system to support them?)
+ Don't take on any commitments that you aren't ready to drive to completion (this goes totally contrary to the "take action on whatever stands out" and "work on it as long as you like" rules)
+ Make sure you craft your tasks either as open-ended tasks that can't be finished so will always get re-entered in C1 ---- or small discrete tasks easily accomplished so they are finished in one go, or stay for a small time in C2 ---- or maybe a few largish tasks ("War and Peace") that will stay in C2 for a long time till they are done. (These are great principles, and "little and often" tends to produce these kinds of tasks anyway, but it requires much more rigor than the fundamental rule, "put whatever you want on the list")
I'm looking for something much simpler, like "if the list is bogging down for you, try entering your urgent tasks on the NEXT page, since this tends to make the system go faster".
Or "try reducing the number of lines in C1 relative to C2, since this will tend to reduce the time you spend cycling through the tasks on any one page".
These are very simple mechanical rules that can make the system move faster and reduce C2 congestion, without the need for frequent invocation of "common sense" rules or introducing new rules that go contrary to the fundamental "in the zone" concepts of Autofocus.
<< I've observed the cumulative effect of C2 myself. It does self correct only in that bad usage yields bad results and you learn from that. >>
That's not self-correction. It's "user" correction. In other words, the system clogs up if there are too many urgent tasks and/or unfinished tasks, so the user must change behavior to accommodate.
<< My suggested remedy is to drop most of the unfinished tasks and resume with a workable load. >>
Yes, that can work, but the problem is, the rules don't allow for that. You must invoke the "common sense rule" to operate that way. That's exactly what I'm trying to avoid. I want the rules themselves to guide me to successful use of the system.
Maybe it's an unattainable goal but still, that's what I'm looking for. :-)
<< Second, knowing the required behaviour, set your mind to operate accordingly, and the problem won't arise. >>
The problem is, this goes against three of the fundamental rules of the system:
+ "enter whatever you want into the list"
+ "work on whatever feels ready to be done"
+ "work as long as you like"
In addition to all these rules, you have to follow a whole bunch more in order to avoid C2 problems:
+ Don't enter too many urgent tasks - or handle them off-list (what if you REALLY DO have lots of urgent tasks? what if it's too complicated to handle them off-list, or you are forced to create a secondary system to support them?)
+ Don't take on any commitments that you aren't ready to drive to completion (this goes totally contrary to the "take action on whatever stands out" and "work on it as long as you like" rules)
+ Make sure you craft your tasks either as open-ended tasks that can't be finished so will always get re-entered in C1 ---- or small discrete tasks easily accomplished so they are finished in one go, or stay for a small time in C2 ---- or maybe a few largish tasks ("War and Peace") that will stay in C2 for a long time till they are done. (These are great principles, and "little and often" tends to produce these kinds of tasks anyway, but it requires much more rigor than the fundamental rule, "put whatever you want on the list")
I'm looking for something much simpler, like "if the list is bogging down for you, try entering your urgent tasks on the NEXT page, since this tends to make the system go faster".
Or "try reducing the number of lines in C1 relative to C2, since this will tend to reduce the time you spend cycling through the tasks on any one page".
These are very simple mechanical rules that can make the system move faster and reduce C2 congestion, without the need for frequent invocation of "common sense" rules or introducing new rules that go contrary to the fundamental "in the zone" concepts of Autofocus.
Reply by Seraphim
Don wrote:
<< I've noticed a kind of oscillation of C2 as you've pointed out, but I don't know what you mean by "system crash". >>
I mean that the system moves so slowly that you can only get through a page or two each day, meanwhile adding 2 or 3 pages to the end of the list each day.
Or, column 2 gets so filled up everywhere that you frequently enter unfinished tasks not on the next page, but 2 or 3 or 4 pages forward.
The system just doesn't work well when these things start to happen. And the system doesn't recover by itself from these problems. The user is forced to invoke "common sense" rules to get out of the problem (e.g., decommissioning lots of C2 unfinished items by moving them to end-of-list C1) or to simply start over.
<< When I got stuck on a page, I was still doing a lot of important work. I ended up finishing or actioning everything on the page before moving on. >>
Yes, I find that happens, too. The longer you stay on a page, the more often you cycle through each task -- and each exposure to a task reduces your resistance to it. So they all tend to stand out after awhile.
I often find myself completing 80%+ of the C1 items on a page, the very first time I arrive on that page. Adding new urgent things on C2 of the current page makes this worse, since I cycle through the whole page a lot more while I'm working those C2 items, and that cycling makes a lot more of the C1 tasks "stand out".
But that's really not how the cycling is supposed to happen. The repeated exposure that breaks down resistance is supposed to happen by means of cycling through the *entire list* many times, clearing a much smaller percentage each time you work through a page. This keeps the whole list fresh, and prevents you from bogging down in the middle, and being forced to endlessly chase the end of the list.
I still get lots done even when moving slowly -- much more than with AF or even DWM. But it just gets slower and slower every day.
<< I've noticed a kind of oscillation of C2 as you've pointed out, but I don't know what you mean by "system crash". >>
I mean that the system moves so slowly that you can only get through a page or two each day, meanwhile adding 2 or 3 pages to the end of the list each day.
Or, column 2 gets so filled up everywhere that you frequently enter unfinished tasks not on the next page, but 2 or 3 or 4 pages forward.
The system just doesn't work well when these things start to happen. And the system doesn't recover by itself from these problems. The user is forced to invoke "common sense" rules to get out of the problem (e.g., decommissioning lots of C2 unfinished items by moving them to end-of-list C1) or to simply start over.
<< When I got stuck on a page, I was still doing a lot of important work. I ended up finishing or actioning everything on the page before moving on. >>
Yes, I find that happens, too. The longer you stay on a page, the more often you cycle through each task -- and each exposure to a task reduces your resistance to it. So they all tend to stand out after awhile.
I often find myself completing 80%+ of the C1 items on a page, the very first time I arrive on that page. Adding new urgent things on C2 of the current page makes this worse, since I cycle through the whole page a lot more while I'm working those C2 items, and that cycling makes a lot more of the C1 tasks "stand out".
But that's really not how the cycling is supposed to happen. The repeated exposure that breaks down resistance is supposed to happen by means of cycling through the *entire list* many times, clearing a much smaller percentage each time you work through a page. This keeps the whole list fresh, and prevents you from bogging down in the middle, and being forced to endlessly chase the end of the list.
I still get lots done even when moving slowly -- much more than with AF or even DWM. But it just gets slower and slower every day.
Reply by Erik
Problem comes from column 1. If you have too many big tasks there (like projects), you will get to a point where you have to start one not to dismiss the page and get stuck with something that sticks in your column 2.
Answer: Smaller tasks in column 1! (stuff that will not linger for more the 3 pages)
Answer: Smaller tasks in column 1! (stuff that will not linger for more the 3 pages)
Reply by Alan Baljeu
Perhaps it was the months I spent last summer doing my own system...
You put it very clearly how the written rules don't allow my exact approach. Yet I feel emboldened to continue, because
a) it works, and
b) the intuition aspect still applies
c) the mechanic are still the same; it's only the subjective part that varies
I might say "things stand out or don't, as influenced by my understanding of the pitfall of overdoing column 2". Knowing I would have to dismiss a page still pushes me to progress on an item ala AF1. Knowing I must continue a started item overcomes my resistance to continuing. Knowing it's important to move toward influences me to say no to the things that cry "maybe". And it works.
You put it very clearly how the written rules don't allow my exact approach. Yet I feel emboldened to continue, because
a) it works, and
b) the intuition aspect still applies
c) the mechanic are still the same; it's only the subjective part that varies
I might say "things stand out or don't, as influenced by my understanding of the pitfall of overdoing column 2". Knowing I would have to dismiss a page still pushes me to progress on an item ala AF1. Knowing I must continue a started item overcomes my resistance to continuing. Knowing it's important to move toward influences me to say no to the things that cry "maybe". And it works.
Reply by Marcus
Seraphim: The urgent tasks provision in SF3 *does not work* outside rather narrow windows of both what an "urgent task" is and how many of them you have. In your case: DON'T DO IT. Manage your daily load of urgent tasks on a separate sheet of paper. Really.
(Use timeboxing to separate urgent work and SF3 work. Set alarms for peace of mind within the timeboxes.)
Once you have your "urgent tasks" outside of SF3, do as Alan said: View SF3 as a game where the goal is to use C2 as little as possible.
(Use timeboxing to separate urgent work and SF3 work. Set alarms for peace of mind within the timeboxes.)
Once you have your "urgent tasks" outside of SF3, do as Alan said: View SF3 as a game where the goal is to use C2 as little as possible.
Reply by Seraphim
Marcus, your suggestion to handle urgent tasks on a separate sheet of paper seems roughly equivalent to my idea of making sure C2 has several lines more than C1. Basically we don't want C2 to clog up with too many urgent tasks. So, take them offline, or make more room for them.
I'll try one of those after I'm done with my experiment of entering them on C2 of the following page. I'm expecting that to provide some relief. If it's not enough, then I'll try reducing the number of lines in C1 (thus increasing the relative number of lines in C2) and/or taking urgent items offline.
I'll try one of those after I'm done with my experiment of entering them on C2 of the following page. I'm expecting that to provide some relief. If it's not enough, then I'll try reducing the number of lines in C1 (thus increasing the relative number of lines in C2) and/or taking urgent items offline.
Reply by Seraphim
Erik,
<< Answer: Smaller tasks in column 1 >>
The AF systems tend to develop that habit anyway. But trying to make a rule out of it goes against one of the more fundamental rules: "enter whatever you want into the list". Just like I don't always have time or attention to break things down into GTD-ish "next actions", I also don't always have time or attention to ask ahead of time, "Am I writing this small enough?"
<< Answer: Smaller tasks in column 1 >>
The AF systems tend to develop that habit anyway. But trying to make a rule out of it goes against one of the more fundamental rules: "enter whatever you want into the list". Just like I don't always have time or attention to break things down into GTD-ish "next actions", I also don't always have time or attention to ask ahead of time, "Am I writing this small enough?"
Reply by Seraphim
Alan -
Yes, the system does tend to teach you things. The threat of dismissal makes some things stand out, that otherwise wouldn't. You are right about that.
That doesn't seem to work the same way, though, for preventing C2 congestion. The action required is specific, and the results are immediate, with the threat of dismissal. The action required isn't quite so clear, and the results are not quite so tangible or so immediate, when faced with the threat of C2 congestion.
If your system works for you, great! use it!! I personally don't want to get into the habit of decommissioning C2 items whenever it gets clogged up, because I have found it takes away some of the effectiveness of having C2 in the first place.
Yes, the system does tend to teach you things. The threat of dismissal makes some things stand out, that otherwise wouldn't. You are right about that.
That doesn't seem to work the same way, though, for preventing C2 congestion. The action required is specific, and the results are immediate, with the threat of dismissal. The action required isn't quite so clear, and the results are not quite so tangible or so immediate, when faced with the threat of C2 congestion.
If your system works for you, great! use it!! I personally don't want to get into the habit of decommissioning C2 items whenever it gets clogged up, because I have found it takes away some of the effectiveness of having C2 in the first place.
Reply by Marcus
Seraphim:
<>
Only roughly equivalent, because a separate sheet does not block page turning in SF.
The way I'd do this: Work on your urgent tasks. If you finish them all, good: Back to SF. If you get blocked or exhausted, you'd schedule a timebox of SF work (until such time you can or must continue urgent work.) You'd be free to turn pages according to SF rules. When the timer chimes, back to the urgent list. And so on. The timer is here so you don't have thoughts of pending urgent tasks distracting you during your SF meditations.
<>
Yes, it does seem that in order to put the focus on finishing, Mark may have sacrificed this property of the AFs. It's a trade-off; if you cheat or tweak it back, you'll probably lose some "focus on finishing."
<
Only roughly equivalent, because a separate sheet does not block page turning in SF.
The way I'd do this: Work on your urgent tasks. If you finish them all, good: Back to SF. If you get blocked or exhausted, you'd schedule a timebox of SF work (until such time you can or must continue urgent work.) You'd be free to turn pages according to SF rules. When the timer chimes, back to the urgent list. And so on. The timer is here so you don't have thoughts of pending urgent tasks distracting you during your SF meditations.
<
Yes, it does seem that in order to put the focus on finishing, Mark may have sacrificed this property of the AFs. It's a trade-off; if you cheat or tweak it back, you'll probably lose some "focus on finishing."
Reply by Alan Baljeu
Ideas for a more forceful C2: You may not look at C1 unless there are less than 3 tasks in C2.
If you have 3 or more, work on some until you have 0-2. Then look at C1, pick one, and resume normal operations.
If you have 3 or more, work on some until you have 0-2. Then look at C1, pick one, and resume normal operations.
Reply by Daouda
Marcus wrote
<<<>
Yes, it does seem that in order to put the focus on finishing, Mark may have sacrificed this property of the AFs. It's a trade-off; if you cheat or tweak it back, you'll probably lose some "focus on finishing." >>
If this is true, it would then mean that SF has lost one of the main assets of the original AutoFocus : allowing one "to explore and let things percolate and develop", as Seraphim wrote in a comment to Mark's SF tip # 4.
However Mark's laconic response to that comment suggests otherwise :
<
<< Is it true that in Superfocus, you can still use Column 1 to explore and to let things percolate and develop, but these kinds of things are really not appropriate for Column 2? >>
Generally speaking, yes.
February 26, 2011 at 21:10 | Mark Forster>>
<<<
Yes, it does seem that in order to put the focus on finishing, Mark may have sacrificed this property of the AFs. It's a trade-off; if you cheat or tweak it back, you'll probably lose some "focus on finishing." >>
If this is true, it would then mean that SF has lost one of the main assets of the original AutoFocus : allowing one "to explore and let things percolate and develop", as Seraphim wrote in a comment to Mark's SF tip # 4.
However Mark's laconic response to that comment suggests otherwise :
<
<< Is it true that in Superfocus, you can still use Column 1 to explore and to let things percolate and develop, but these kinds of things are really not appropriate for Column 2? >>
Generally speaking, yes.
February 26, 2011 at 21:10 | Mark Forster>>
Reply by Marcus
Daouda: Mark is of course right, generally speaking, because you can enter tasks such as "explore X for a short while" or "develop Y, a little, maybe" or "let Z percolate a bit". But unless you enter everything with such proviso, you have to think about whether you want a thing explored or done *before* you enter it. You have to pre-plan your entries. Entering without thought, not having to pre-plan, was how I understood Seraphim's "enter whatever you want into the list".
Reply by Alan Baljeu
Your understanding is quite incorrect Marcus. You totally do not pre-plan your entries.
"Entering without thought, not having to pre-plan" is EXACTLY what you're supposed to do.
I can enter anything I want any time, and reenter it any time, change it, refine it, split it, think about it, whatever. This is essential to Autofocus, and still applies to column 1.
"Entering without thought, not having to pre-plan" is EXACTLY what you're supposed to do.
I can enter anything I want any time, and reenter it any time, change it, refine it, split it, think about it, whatever. This is essential to Autofocus, and still applies to column 1.
Reply by Marcus
Alan, according to the rules it doesn't matter if you select a task from C1 or C2. So either you have to finish it as written, regardless of column, or you don't. Combined with Mark's remark that "the system forces you to finish tasks once you've started them.", I think he must have intended the written task description to be pretty much binding. Where's the force, otherwise?
Reply by Erik
Alan, while I agree with you that you can, in most ways, put anything you want in the system, I have to point out that Marcus is right in what he is saying. Most of Mark's advice on SF3 is that you have to define what done means before starting the task and entering it in C2.
My advice is not to define it at entry but when you star to work on it. Let it percolate all you want and when you feel the time is right to move on it, define what that entails before you write it in C2.
My advice is not to define it at entry but when you star to work on it. Let it percolate all you want and when you feel the time is right to move on it, define what that entails before you write it in C2.
Reply by Alan Baljeu
I agree 100% with that advice. If the rules as written forbid refining of tasks entered, they were written incorrectly, because that's contrary to Mark's intention to allow intuition. The only point where it matters to have a precise scope is if it enters column 2.
Reply by Daouda
Mark wrote
<>
If this is true (I cant tell, I havent tryed SF yet), then it should definitely have been part of the SF instructions, formulated as clearly as you just did, even better with some specific examples. Especially for the folks that are coming from AF1 etc.
If your interpretation of the rules is correct, it also means that you cannot use the SF list as an instant "ubiquitous capture tool" for any action-related thought anymore.
This changes (restricts) the possible use of the list, and would make the addition of some "instant capture" list almost necessary, which is precisely the kind of overhead, unneeded with AF1, that Marks seems to avoid with his systems.
Let's see :
If one wants to instantly capture such actionnable thoughts that he is unsure about wether doing or simply exploring, then I guess he should do something like using the back of the SF notebook for this (capturing these "tasks"), and enter a recurring task along the line of "review stuff at the back of the notebook".
During that "review" a decision would be made about the tasks which should then be entered (or not) into the SF list with the adequate formulation. "Tasks" not transferred to the SF list could be deleted forever, or left there for the moment, or put in a tickler/outlook reminder for later entry... Maybe even transferred to a longer-term, more thought-out "dismissed-pending-someday/maybe-whatever" folder reviewed weekly. [Although this is probably superfluous and redundant, and the 2 lists - back of book "rough thoughts" with "dismissed-someday" folder - should better be combined somehow?]
This so we could keep the benefit of being able to write stuff down immediately without pre-planning... at the expense of quite some additional overhead vs AF1. Note that another benefit would be to keep the main list shorter vs AF1 (some stuff would be pre-dismissed or deleted). It could prove awkward in practice though. Or maybe, even worse, what i just wrote doesnt make any sense since making the decision about wether "enter in C1" or "write in the back of the notebook" is pretty much the same than deciding to either write "do X" or "Explore X"... Argh
Marcus, I hope you are wrong and Alan is right. Only Mark will tell us though...
<
If this is true (I cant tell, I havent tryed SF yet), then it should definitely have been part of the SF instructions, formulated as clearly as you just did, even better with some specific examples. Especially for the folks that are coming from AF1 etc.
If your interpretation of the rules is correct, it also means that you cannot use the SF list as an instant "ubiquitous capture tool" for any action-related thought anymore.
This changes (restricts) the possible use of the list, and would make the addition of some "instant capture" list almost necessary, which is precisely the kind of overhead, unneeded with AF1, that Marks seems to avoid with his systems.
Let's see :
If one wants to instantly capture such actionnable thoughts that he is unsure about wether doing or simply exploring, then I guess he should do something like using the back of the SF notebook for this (capturing these "tasks"), and enter a recurring task along the line of "review stuff at the back of the notebook".
During that "review" a decision would be made about the tasks which should then be entered (or not) into the SF list with the adequate formulation. "Tasks" not transferred to the SF list could be deleted forever, or left there for the moment, or put in a tickler/outlook reminder for later entry... Maybe even transferred to a longer-term, more thought-out "dismissed-pending-someday/maybe-whatever" folder reviewed weekly. [Although this is probably superfluous and redundant, and the 2 lists - back of book "rough thoughts" with "dismissed-someday" folder - should better be combined somehow?]
This so we could keep the benefit of being able to write stuff down immediately without pre-planning... at the expense of quite some additional overhead vs AF1. Note that another benefit would be to keep the main list shorter vs AF1 (some stuff would be pre-dismissed or deleted). It could prove awkward in practice though. Or maybe, even worse, what i just wrote doesnt make any sense since making the decision about wether "enter in C1" or "write in the back of the notebook" is pretty much the same than deciding to either write "do X" or "Explore X"... Argh
Marcus, I hope you are wrong and Alan is right. Only Mark will tell us though...
Reply by Daouda
Alan, I seem to have somehow pushed the thread off-topic and the attention away from your last, very interesting idea :
<If you have 3 or more, work on some until you have 0-2. Then look at C1, pick one, and resume normal operations. >>
Have you tryed this yet?
<
Have you tryed this yet?
Reply by Lillian
Marcus < So either you have to finish it as written, regardless of column, or you don't. Combined with Mark's remark that "the system forces you to finish tasks once you've started them.", >
I'm not so sure, in Mark's ProgessReport #2 blog entry ( http://www.markforster.net/blog/2011/2/22/whats-next-progress-report-2.html ) it looks to me like the entry is written as "What Next List" He did some work, and I assume then crossed it off and re-wrote it on the appropriate space. That doesn't look like a task description that was pre-planned before being written down
I'm not so sure, in Mark's ProgessReport #2 blog entry ( http://www.markforster.net/blog/2011/2/22/whats-next-progress-report-2.html ) it looks to me like the entry is written as "What Next List" He did some work, and I assume then crossed it off and re-wrote it on the appropriate space. That doesn't look like a task description that was pre-planned before being written down
Reply by Seraphim
Marcus wrote:
<<< Work on your urgent tasks. If you finish them all, good: Back to SF. If you get blocked or exhausted, you'd schedule a timebox of SF work (until such time you can or must continue urgent work.) You'd be free to turn pages according to SF rules. When the timer chimes, back to the urgent list. And so on. The timer is here so you don't have thoughts of pending urgent tasks distracting you during your SF meditations. >>>
Thanks Marcus! I've added an Outlook reminder for me to try this if my current experiment doesn't bear fruit.
(Though I must admit, whenever I try using timeblocks, I can almost guarantee I'll do ANYTHING except what the time block was originally intended for.) :-)
<<< Work on your urgent tasks. If you finish them all, good: Back to SF. If you get blocked or exhausted, you'd schedule a timebox of SF work (until such time you can or must continue urgent work.) You'd be free to turn pages according to SF rules. When the timer chimes, back to the urgent list. And so on. The timer is here so you don't have thoughts of pending urgent tasks distracting you during your SF meditations. >>>
Thanks Marcus! I've added an Outlook reminder for me to try this if my current experiment doesn't bear fruit.
(Though I must admit, whenever I try using timeblocks, I can almost guarantee I'll do ANYTHING except what the time block was originally intended for.) :-)
Reply by Seraphim
Alan wrote:
<<< Ideas for a more forceful C2: You may not look at C1 unless there are less than 3 tasks in C2. If you have 3 or more, work on some until you have 0-2. Then look at C1, pick one, and resume normal operations. >>>
I've also added that as an Outlook tickler, to try if my current urgent-on-next-page-C2 experiment doesn't work out.
<<< Ideas for a more forceful C2: You may not look at C1 unless there are less than 3 tasks in C2. If you have 3 or more, work on some until you have 0-2. Then look at C1, pick one, and resume normal operations. >>>
I've also added that as an Outlook tickler, to try if my current urgent-on-next-page-C2 experiment doesn't work out.
Reply by Seraphim
Marcus wrote:
<<< But unless you enter everything with such proviso, you have to think about whether you want a thing explored or done *before* you enter it. You have to pre-plan your entries. >>>
I suppose this depends on what your "default meaning" is for vaguely-written tasks.
My own default is "this task means explore, develop, percolate unless otherwise designated".
Thus if I write "Project XXX", it means "think about Project XXX, explore Project XXX, do a little work on Project XXX".
Thus it would always be re-entered in Column 1 on last page.
And, I can re-enter it in a new form if I want:
+ "Ask NNN about Project XXX" (which is written more specifically and concretely and would normally be a C2 task if left unfinished)
+ "How does Project YYY relate to Project XXX?" (which is another open-ended, re-enter on C1 last page kind of task)
If I want to make sure it gets the C2 treatment, I can write it differently: "Finish Project XXX". This one would end up in C2 if not finished in one go. And this is where I need to be careful how I write things.
I do this with my email. Sometimes if I just want to do a quick check, I'll write "Email". If I want to give it the full treatment, I write "Clear email".
If you want, your "default" treatment can be "this is always a C2-type task unless otherwise designated". So, if you write "email", it would mean "clear email". If you wanted it to be looser, you could write "check some email".
I guess the Action Item for everyone doing SF is to decide: "What is my default task treatment?"
<<< But unless you enter everything with such proviso, you have to think about whether you want a thing explored or done *before* you enter it. You have to pre-plan your entries. >>>
I suppose this depends on what your "default meaning" is for vaguely-written tasks.
My own default is "this task means explore, develop, percolate unless otherwise designated".
Thus if I write "Project XXX", it means "think about Project XXX, explore Project XXX, do a little work on Project XXX".
Thus it would always be re-entered in Column 1 on last page.
And, I can re-enter it in a new form if I want:
+ "Ask NNN about Project XXX" (which is written more specifically and concretely and would normally be a C2 task if left unfinished)
+ "How does Project YYY relate to Project XXX?" (which is another open-ended, re-enter on C1 last page kind of task)
If I want to make sure it gets the C2 treatment, I can write it differently: "Finish Project XXX". This one would end up in C2 if not finished in one go. And this is where I need to be careful how I write things.
I do this with my email. Sometimes if I just want to do a quick check, I'll write "Email". If I want to give it the full treatment, I write "Clear email".
If you want, your "default" treatment can be "this is always a C2-type task unless otherwise designated". So, if you write "email", it would mean "clear email". If you wanted it to be looser, you could write "check some email".
I guess the Action Item for everyone doing SF is to decide: "What is my default task treatment?"
Reply by Alan Baljeu
Daouda, I wrote in other threads how I consciously limit myself to one or two tasks active in C2. As a result, having 3 or more active rarely occurs. This rule is for someone who wants that effect governed by a rule.
Reply by Alan Baljeu
"What is my default task treatment?". Free association.
I write whatever. When I read it, I make whatever sense fits the words,the situation, and my time. I may rephrase it if that helps in sense-making, or alter it if it makes it more pertinent.
I write whatever. When I read it, I make whatever sense fits the words,the situation, and my time. I may rephrase it if that helps in sense-making, or alter it if it makes it more pertinent.